Hi Abu,
Thanks for the inputs, before I comment on checking the autodiscover config. I would like you to check the below post link(Sorry my earlier link was pointing somewhere else)
Ex2013 works differently and hence you can no longer use a CAS Servername or alias to configure a account like earlier versions. You need to input the unique ExchangeGUID for the mailbox.
Refer to this link for
Manually configure Outlook for Ex2013
Once we confirm that Exchange is setup correctly we can focus on autodiscover part. Which is the only means users can configure automatically for Ex2013 accounts on OUtlook.
To test it simply open this URL using IE. See if you get some XML data with Invalid error. IF yes Autodiscover is fine (initial test atleast)
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml
Basically the autodiscover should be pointing to Ex2013 IP and not Ex2010. Ex2013 in co-existance scenario is aware and would automatically proxy the requests to Ex2010
In the EAC, go to Servers > Virtual directories. Verify all the directories are updated with the primary URL meant for Ex2013 in
Internal URL ,External URL .
You can run this to confirm and check if you have correctly configured all pre-requisites and post-migration task correctly.
Microsoft Exchange Server Deployment Assistant
When you run this command in Ex2010 the external hostname should be Ex2013 server URL.
Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 14*") -And ($_.ServerRole -Like "*ClientAccess*")} | Get-OutlookAnywhere | Format-Table Server, ClientAuthenticationMethod, IISAuthenticationMethods, SSLOffloading, ExternalHostname -Auto
This command should also listing SCP Ex2013 for both Ex2010 and Ex2013 cas.
Get-ClientAccessServer | Format-Table Name, AutoDiscoverServiceInternalUri -Auto